Ensure that private members do not cause problems between debug/release versions

[erik-kallen]

In the 3.x branch, the name of private members get burnt to the class using a [UsedMemberNamesAttribute]. This means that when building a release assembly referencing a debug assembly (or vice versa) and deriving from a type in the other assembly, there is a risk for a member name collision.

Possible solutions include:

1. make the [UsedMemberNames] have different lists for minified and non-minified scripts.
2. name all non-public class members like $x$theName, where x is the depth of the class hierarchy of the type. Note that internal interface members need not have this applied to them because they are not minified in release builds.