I know the next thing people will say is find better clients, but some people just have expertise in areas where the clients tend to be smaller and more cash-strapped. Thankfully the work is interesting.
Right now I give estimates, but still provide hourly billing as a safety net. Once I'm confident that my estimates are consistently accurate, I might move to project based billing, but it also feels a bit sleazy because what I would do at that point is just take ESTIMATE x SOME MULTIPLIER. In other words, project-based billing sometimes sounds like a hand-wavy way to charge the customer more without them being able to tell.
I prefer time based billing, because I don't work 8 hour days like normal people. For this reason I also make sure I'm working on things that can be done in those timeslots, and I'm very, very conscious of the client's time.
I think either method is fine as long as you're comfortable with it, and you're on the same page as the client.
I know per-project billing is fraught with its own issues, but I'm much more a fan of that vs. time-based billing. It may work out to cost the client more, but it removes that layer of distrust ("is my engineer taking longer to squeeze more money out of me?") and sets the incentive on the worker to get the job done as quickly as possible, since now taking longer becomes the disincentive.
I believe the only folks who should bill hourly are the ones who do jobs where performance of work duties is directly correlated to hours spent working -- i.e. where doing a job "faster" doesn't change the time required. Security guards, retail workers, etc.
I'm sure there are a ton of fallacies in the above arguments, so let's hear 'em...