I have never seen this behavior. Maybe the database is corrupted. I would recommend creating a new replica on another server, deleting this one, and making a fresh replica in its original location. I did see completely bizarre @modified behavior two weeks ago that was repaired in this manner. (big database, very painful – hopefully your database is small and this fix is very quick).