Hmmm... I guess I do not understand how renaming the object in the model would have any impact on the name of database object... they are independent objects, from different models!? Anyway, we will take a look at it & hope we can reproduce it.
In meantime... are you familiar with the manual matching feature in Model/Database Compare? There are situations when, despite the tool's best guess, objects that should be matched are not matched because the tool is lacking the contextual/specific information to make such decision.
For instance, let’s assume you have a table X in your model and while initially was forwarded as X in the database, someone decided to rename the table as Y. Now, when doing the database compare, X and Y are not matched since they have different names, but they should, so you can import the rename from the database into the model. This is where manual matching/un-matching comes handy. You use the feature the match X and Y and then import Y into the model (and therefore renaming X to Y).
So, for your particular problem, as a workaround, you can manually match Valid Values 1 and Valid Values 2.
Hope this helps.
ModelRight Evangelist