Code editor rewrites typed member names to the casing of an unrelated same-named member

The code editor's automatic formatting can change the casing of a correctly typed member name. If the same member name is declared more than once in a project with different casing (for example an enumeration value _MemoryBlock and an unrelated property _memoryBlock), the editor adopts one of those spellings as the single project-wide casing for that name and rewrites correctly typed usages of the other spelling as you finish each line. The declarations themselves are unchanged, so the source ends up using a different casing from the declaration it refers to.

Expected behaviour: a member name typed with the same casing as its declaration is left alone, and in particular a declaration's casing is never overridden by an unrelated same-named member elsewhere in the project.

Reported with an enumeration whose _MemoryBlock value kept being un-capitalised to _memoryBlock while typing usages, even though the enumeration definition still declared _MemoryBlock.