> An STL vector is good for single threaded stuff and > even then you need to be very careful with it (it has > the tendency to call the copy constructor of the > value's class in order to move objects around)... Well, you'd be in a world of hurt if it didn't! Moral: don't expect top performance from blindly using containers on classes that have copy constructors. -- jm