Yes - my compiled code is separated...
By the way, my current workaround for this is the old "pre-save, change, check, re-save" routine.
Pre-saving the project before making any changes is starting to become second nature before editing any enum typedefs.
Checking is a pain if you're paranoid, but usually I can tell if morphing has occurred by looking at any one instance. There seems to be an all-or-nothing pattern here...
If there is suspicion, then I have found that saving the enum and then reverting the entire project usually does the trick, i.e. the morphing seems to be an edit-time effect and generally does not occur if the project is re-opened with a modified enum. (At least, this is what I have seen when adding values or deleting unused values...)