I've been wracking my brain cells (all 3 ;o) to work out why I wouldn't do it this way as I don't and I guess I need to justify why I don't!
So here goes my thoughts...
1. You can only ever have one container class.
2. You could find that extending the class to deal with new features may be more complex than needed, for example Sorting the list, ToString.
3. Encapsulating changes is a good way to work with OO this approach might get in the way of this (see 2).
Apart from that I kind of like it as it obeys the K.I.S.S. rule "Keep It Simple Stupid" which for some bizarre reason I often forget!
So here goes my thoughts...
1. You can only ever have one container class.
2. You could find that extending the class to deal with new features may be more complex than needed, for example Sorting the list, ToString.
3. Encapsulating changes is a good way to work with OO this approach might get in the way of this (see 2).
Apart from that I kind of like it as it obeys the K.I.S.S. rule "Keep It Simple Stupid" which for some bizarre reason I often forget!