If you like.

If you have a 1-1 mapping of view to container, it's easier to switch the view.

If you have a 1-n mapping of view to container, thats fine too, but when you "switch" container, your app will temporarly "disapear" (that is its client area will go transparent, and you will be able to see whats underneath, usually the menu) and then the new container will appear when you show it.

You can avoid that by creating the new container first, before destroying the old one.

However, more often than not, people use containers when they don't really need to - if you have one control which fills the entire view (say a list box) you DONT need a container.  Containers (in this sence) are for so called compound controls - ones which contain more than one sub control (Think CountComponentControls and ComponentControl).

>Unless you want to override some keys etc...

Yes - though in that case you could also just subclass the list box.