The rule PSUseShouldProcessForStateChangingFunctions is far too simple

You can't determine if a command is "State Changing" based purely on the verb. This is the sort of stuff that makes me SO upset at this module that I just want to throw it out -- it takes too much time to go through and review stuff when most of the warnings/errors are wrong.

For one example, I'm getting that warning on a bunch of XML document commands like "New-XElement" and "New-XAttribute" which obviously don't modify system state, they just create xml nodes and attributes which can at least hypothetically be added to a document in memory.

For another example, almost every single command in the ShowUI module uses the "New" verb to generate UI elements on windows, not to modify the system state.

Start by reviewing the PSUseShouldProcessForStateChangingFunctions rule and the reported cases New-XElement, New-XAttribute, and ShowUI commands. Determine how the rule should distinguish commands that create in-memory XML or UI elements from commands that change system state, then add coverage showing that the false-positive warnings are gone.