I've noticed a bug in ReSharper 5.0's Code Cleanup that is causing a breaking change to my application after running.
My solution is setup such that I have two classes called "Utilities", each one in its own project. I have a class file that references the "Utilities" class from both projects and in order to select the correct one I am explicity defining the namespace "Helpers.Utilities" for static method calls to that class. After running Code Cleanup ReSharper is removing the "Helpers" namespace definition from the call into the "Utilities" class, which causes the code to instead point to the wrong class. Additionally, when the Code Cleanup runs it adds a "using Utilities = Type.Path.To.Utilities;" to the top of the class and, I assume, it then blindly infers that the using definition means that there is only one Utilities and thus the namespace prefix ("Helpers") is redundant.
This is happening in ReSharper 5.0.1601.21.