Has anyone else found themselves doing the following:

      public class FooList : System.Collections.Generic.List<Foo>


Rather than just using or exposing the List<Foo> type directly?  For some reason I prefer the strongly type name.  True, I would most likely expand on this class for such things as an overloaded Add() method, etc. Anyone see anything wrong with this? Will you end up with too many (trivial?) classes to maintain?