This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I think you should not worry about these numbers. For instance, I finished with 5 packages (and other 4 packages inside them), 56 classes and around 2000 lines of code. I think you should only worry if you have to many inner classes, and too many classes with too much code. I would say that this may be considered in the OO Design part of their evaluation.
Well, I would avoid this, you know... take a look at this article: http://developers.sun.com/mobility/midp/articles/slimming/. Even though it is about wireless Java applications, the behavior of the JVM theoretically is the same (in this case), and they do advise to avoid inner classes. I've also seen many discussions around the software engineering comunity, where people tend to avoid inner classes. I do too because I believe it makes the code more cohesive, maintainable, reusable and readable.
I also have a big number of classes because many of them are interfaces, and I created several components as well.