Visual Studio Add-In always tries to change the visual studio project file after saving a file with Q_OBJECT in it...

We are using Visual Studio 2005 and the non-commercial add-in version 1.1.1.

Everytime I save a file which has the Q_OBJECT macro in it, the QT macro tries to get write access to the visual studio project file and it changes almost every entry in it, even if for this file the custiom build steps for moccing already existed.

This is very annoying, since the project file is difficult to merge and qt changes the position of almost every entry.
Second, we are quite a few people working on the same project and and visual studio has an exlusive lock in our source control system because of the merge situation. Now, everytime I save a file, it tries to get the lock of the project.

Why do you not first check, if the entry in the project file is already there and correct and only write to the project file, if there are changes to be made?