Everywhere I've worked there's only a few levels where you actually code - right now we have graduate, dev, and senior dev. You'd end up moving your best people to a level where you can't use their skills any more.
Also the up-or-out policy has exceptions: there are "stable" levels where you are allowed to stay for the rest of your career. IIRC the lowest stable level is Senior Dev (level 63) so if you are hired at level 59, the expectation is that you have the potential to make it to 63; if you earn promotions too slowly or not at all, you'll eventually be let go. This is true even if you do a perfectly adequate job at levels 59-62.
It's not a model that would work for every company, obviously...
At my not-particularly-good university they keep hiring faculty at assistant professor rank. Since the graduate school isn't impressive the applicant quality and publication record isn't great, and someone getting a grant is a rarity. After five years they won't get tenure, the position is re-advertised, more startup money is spent, wash, rinse, repeat. Under these circumstances it would be wiser for them not to shoot for the star performers they won't ever get. The research quality will be just as mediocre, but they can spare themselves the hiring process and save on startup funds.
http://en.wikipedia.org/wiki/Up_or_out