The most probable cause of your AV warnings was likely a poorly chosen virus signature by either your chosen AV provider, or the central clearinghouse of AV signatures (a resource subscribed to by nearly all AV vendors).
Over the past couple of years I have witnessed a number of instances where AV signatures were generated against code snippets from the MSDN (Microsoft Developers Network) and related sources. These code snippets and sample routines are used by many software developers.
Unfortunately, they are more likely to appear in legitimate code than illegitmate. But, since exploit developers also have access to these same resources, they occassionaly cut and paste these code samples into their exploits.
Then someone reports the exploit to an antivirus vendor, who then incorrectly latches onto the sample code when they create their AV signature and ... presto ... legitimate software starts getting flagged as a virus or other exploit.
In recent years I have had my accounting software partially wiped out by antivirus software for the same reason. I have also had a number of Microsoft Resource Kit utilities wrongfully flagged as exploits by AV software as well -- all due to poorly chosen AV signatures... even Yahoo Messenger is actively flagged as a keylogger by some AV vendors.
Sometimes these issues will resolve themselves if the AV vendors catch onto the mistake and rescind the signature, other times the only action you can take is to exempt that particular item from AV scanning by using your AV softwares provisions for user-defined exceptions.
Good luck!
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET CLR 1.1.4322; OfficeLiveConnector.1.4; OfficeLivePatch.1.3)
