Thanks for your post. I've double checked with the dev team, and there are some other factors coming into play that are messing this up for you.
In the simplest terms, performing the restore over the DB that was already linked caused the working base to be different to the restored DB (it was already successfully synced with the DB prior to the restore, and also synced with the source control system).
Since that happened and the working based and source control system were the same, SQL Source Control did its thing and made the call that you had made a change to the DB, that needed checked in.
If your working base had been in a different state to the revision in source control, then SQL Source Control would have prompted you for a get latest.
It's not really ideal behaviour to perform restores, but if you must do it the simplest thing is to unlink and then re-link the DB after it's been restored. When you do that, your working base will be at the same revision as that of the DB, but less than your source control system.
You should therefore, in that instance, be prompted to perform a get latest.
Red Gate Software Ltd
+44 (0)870 160 0037 ext. 8569
1 866 RED GATE ext. 8569