No. You actually don't add an object to the list, but a reference to it. That means you can add it to lot of different collections, but all of them will point to the same object, and if you change it, all the collections will point to the same changed object.

If you want the objects to be distinct, just create two objects.
If the object already evolved and you want a copy/snapshot of the current state, you can make a copy constructor (preferred to clone() whose behavior in unreliable):

1. class Foo
2. {
3.   int x, y;
4.   Bar bar;
5.  
6.   // Regular constructor
7.   Foo(int xval, int yval)
8.   {
9.     x = xval; y = yval;
10.     bar = new Bar(x + y * width);
11.   }
12.  
13.   // Copy constructor
14.   Foo(Foo f)
15.   {
16.     x = f.x; y = f.y;
17.     bar = new Bar(f.bar); // Use the copy constructor of Bar!
18.   }
19. }

ahh so it's somewhat like pointers in C?

I still remember some of my C.... C is a nasty language, but it's fast.

It is indeed similar to pointers, except that such references are much safer than pointers! You can't point at arbitrary areas of memory, only at existing objects.