There are no good source control integrations for Visual Studio. The whole system is just fundamentally broken. If you're not convinced - I mean you in general, dear reader, malkia clearly has this figured out ;) - all I have to say to you is, "LOL binding root".
Over the years, I've managed to convince several people to give up Visual Studio source control integration, and, without fail, it takes them two days, at most, to realise that this one small step has made their lives MEASURABLY BETTER. After weeks, maybe months of laughing at my Alt+Tabbing to Alien Brain to check files out, or fumbling with p4v, they find out that this is still better than dicking about with whatever crap Visual Studio is pulling on you today.
Well, I'm guilty of shooting my mouth off about something I haven't revisited recently, so perhaps things are better these days. I haven't used source control integration with VS2010 or VS2012. Sometimes, when I find something to suck, I still revisit it every now and again, just in case it's since improved. The Visual Studio source control integration experience was just so reliably, hellishly awful that I never saw the need.
(The experience could well be better if you have a distributed system. Much of the plugins' flakiness seemed to be come from having to talk to a server (downtime or network connectivity problems always caused issues), and from the maintenance of accurate check in/check out information - both non-issues with a distributed system.)
Have used both ankhSVN [1] w/ VS2008 extensively over the last few years and lately using Git Source Control Provider [2] w/ VS2010. Both tools have been excellent for me, have very rarely needed to drop down to external tools. YMMV
Over the years, I've managed to convince several people to give up Visual Studio source control integration, and, without fail, it takes them two days, at most, to realise that this one small step has made their lives MEASURABLY BETTER. After weeks, maybe months of laughing at my Alt+Tabbing to Alien Brain to check files out, or fumbling with p4v, they find out that this is still better than dicking about with whatever crap Visual Studio is pulling on you today.