You should move up the hosting chain as your needs demand it, and not before. Yes, you'll pay more for cloud-hosted solutions, but if one of the racked servers has a power supply failure or a motherboard failure or bad RAM or a failed drive, that's their problem to deal with, not yours -- and at the moment, most of the cloud providers seem to be very good at dealing with it.
All of those things are a distraction, and worse still, if you don't have multiple layers of redundancy -- which will add to your costs -- then they can result in down time for your service, which is bad.
I, personally, would not move to a dedicated server until the costs for required resources became so egregious in the cloud that I could no longer afford not to use a dedicated server.
Secondly there is actually little difference between the amount of time spent managing a VPS versus a dedicated or colo. Hardware failures aren't going to be your biggest concern. It's going to be services going down, database misbehaving, OS misconfigurations, general scaling issues, network dropping out etc e.g. witness all of the AWS/Linode outages almost all of which are due to DC power/networking.
And the fact is that my Mac Mini has an equivalent Unixbench/disk test as the Linode instances + AWS m1.xlarge. So it gives you an idea of how much better performance and value you will get from a dedicated or colo.
You should be as transparent as you expect other entities to be.