Microsoft has confirmed that this is bug with VS 2005. So we can keep
our fingers crossed till they give us the solution.

Refer the link for more details
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=2ce60503-bf84-44d0-af9f-ee26b6f1ad21

--
Thanks
Arvind