The CPU power available to crackers has increased to the point that salting is no longer adequate;
Guess it depends on how interested they are in getting at those password. But then, twas always the same it just took longer. Salting was never a panacea anyway, the intention is only to slow the buggers down.
It also makes things a lot harder for them if you use a site-wide salt and per-user salts.
Hell, there are even additional techniques you can do to help slow them down further. If they've only managed to get db level access, would they know that every vowel in the users password is automatically replaced with a hash of something else? (Not that I'm advocating security by obscurity here, but it can help as part of a solution).
Using strong passwords also helps, as a proper password is less likely to appear in the rainbow tables in the first place. So barring hash collision still wouldn't have been cracked. That would, of course, mean users realising that "drowssap" is not a good token to use.
Not that I'm saying the likes of bcrypt etc shouldn't be used, just that your assertation that you need to use them isn't entirely accurate. You should use them, but we're not yet at the point where proper salting is completely pointless (though when we do reach that point, I suspect a lot of people will continue to use only salting!)