We are considering removing it locally, as the static analyzer erroneously generates warnings of that type for some of our code. (I can elaborate if you wish)
Before we remove it, we’d like to consider the intent/reasoning behind the original change.
Epic adapts the code to be compliant with the static analyzer, there’s not more reasoning for this change than that in this case. We’ve seen some false positives but since we don’t own the visualcpp static analyzer we’d rather be compliant with these than not block on the errors for the true issues.
If your organization wants to work differently it’s very much ok to change that configuration, that .ini is provided as a sample that every company can modify to their requirements.