The pain, I presume, is that you break things while you didn't think so. Unit Testing tells you what situations will break when you refactor. Shouldn't feel like bathtub kitty so much anymore.

I know what Unit Tests are and the fact is that I use them, they still don't make refactoring easier...
Granted, making sure that everything works afterwards is easy, but I dare you to refactor a large project which usually looks like:
10 Minutes: "Mhhh, okay, I will just change this and ever..."
120 Minutes: "Whoops, well, okay, I see, this depends on this... Uhm, okay, lets change this too and"
180 Minutes: "WTF, why is this method/class used all over the place? Okay, lets change this too"
3 Days: "OMGWTF HAVE I DONE?!!"
2 Weeks: "Can I please discard all the changes I have done and we forget this whole refactoring stuff?"

You can't win your 2 weeks back, but ofcourse you use source control to roll back your code .

If unit testing alone doesn't work out for you well enough, perhaps add code coverage? Haven't tried it, but seems to work for this sir:
http://www.ericsink.com/articles/Code_Coverage.html

Joozey, doesn't really work with libraries, eh?
And yes, my source control can roll it back, thats exactly what I was implying with my last line ^^

@Pappenheimer: THAT is really impressive!

@Pappenheimer: I loved it! :>

Greatest voice crack in history:

http://www.bildschirmarbeiter.com/video/die_stimme1/