I don't do it just because calling people "resources" is dehumanizing, I also do it because I think this attempt of reducing complexity is naive. You can treat people the way you treat other items on a timesheet, sure, and you might even get a great deal of satisfaction from it, because you're so cold-hearted and professional that a drop of blood just harvested from your aorta could turn the global warming problem into a neverending winter problem if it's dropped over the North Atlantic. That doesn't make it a smart thing to do though. People aren't resources in the classical sense. They aren't predictable and "budgeting reserve time" is not the correct approach to deal with that. Encouraging and nurturing the kind of behaviour that a project depends on is a far better approach.
Treating us nicely is just a means to the same end of them making money from us. Such is the problem of individual ownership, instead of worker ownership.
I hear this from managers and project coordinator types, not from fellow hackers, so I'm probably preaching to the choir. It might help to prudently point out dehumanizing language when we hear it.