I think it would be better to put it this way - if you care about $100/month, you should consider co-locating. Otherwise, you need other reasons.
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.
One of your key points is what turns some people towards more managed services: "skills to support it". I'd add time to that factor as well.
If I had the support staff, I would co-locate in a second. Heck, one of our previous locations was next-door to a Level 3 co-location facility. It was pretty nice to be able to walk 10 feet and access your hardware.
Nitpick: Vagrant is not a deployment system. It's an awesome tool, but it falls back to puppet/chef for the actual configuration.
For $100 I could get a Xeon E3-1245 with 32GB ECC Ram, 2x 3TB HDs from Hetzner. One year later? Better system, same price. Upgrade costs? One to two days of work migrating.
I believe co-location has its place but not if we are talking about "only" $100 and pretty simple needs. There is always a time factor that outweighs its gains.
"Hostage situations" and incompetent personal is something, I believe, that is hard to compare. Everyone near your system, no matter what or where, can cause problems.
What if they refuse to hand out your server till all payment problems are solved? Maybe this depends on the country but getting the server if they refuse to hand it out will likely consume more time than just paying whatever they want. Also if you planned for this situation with some EC2 instances just switching the domain over and settling the dispute should be doable.
For my side-projects, personal websites and general purpose "whatever" I'm using an in-expensive colo provider(Colo@). For $50 I get 10mbit/s @ 95% (basically, burstable to 100mbps for up to 5% of a month). That's about 3 TB of data transfer which alone would cost hundreds of dollars at EC2. Of course, it is also way more data than most people would use.
The server I bought used on eBay for $365. Its a dual Xeon L5420 (8 hw cores) and has 24 GB of RAM. I run seven or 8 VMs under KVM on it presently. These images are pretty portable and a couple of them I backup regularly to S3; I could recover to an EC2 instance if I lost the box.
I monitor this with an EC2 micro instance and have not had any network outages in 6 months there. If I wanted to run a production site there I would need at least a second machine for redundancy; that would be another $30-40 a month. I'd probably also replicate real-time to a small EC2 instance so that would cost a little (though the incoming B/W to EC2 is free) - I don't do that now as I don't have real "production" data.
Not everyone should do this but if you like servers you should consider it. Another advantage here is that I own the server. If I get in a billing dispute or other issue with my provider they can take me off the network but they cannot hold my server hostage. Also they cannot login to the box - any attempt at social hacking is pretty well doomed.
On the other hand, on the two occaisions I've needed remote hands and the one time I needed a KVM they responded in less than fifteen minutes. It is mind-blowing the level of support you can get with the right provider.