I think this could be the article you're thinking of: http://www.gamearchitect.net/Articles/GameObjects1.html
It makes some good points, though at times it's a bud FUDdish about inheritance. Some of the problems mentioned with inheritance were just poor design decisions. Still, unless your game is never going to be extended and fits an inheritance model perfectly, the aggregation approach seems the way to go.
The real killer comes down to not having multiple inheritance. When different classes need to share more than one bit of code, that whole model falls apart.