C++ design pattern

Can you help me? I'm wondering what is the best pattern for the situation I'll describe.

SITUATION 1


class Inside {
  public:
    Inside(int a, int b) {
        yada = a;
        foo = b;
    }
    int yada;
    int foo;
};

class Container {
  private:
    Inside *c;
  public:
    Container(Inside *i) {
        c = i;
    }
    ~Container() {
        delete c;
    }
};

This situation allows you to avoid deleting the parameter passed as argument, so you can do:

Container c(new Inside(10, 20));
and the Inside instance will be deleted automatically. Drawbacks following:

Inside i(10, 20);
Container c(&i);
FUCK, i've deleted the stack!

SITUATION 2


class Inside {
    ...
};

class Container {
  private:
    Inside *c;
  public:
    Container(Inside *i) {
        c = i;
    }
    ~Container() {}
};

Now you can do:

Container c(new Inside(10, 20));
but you get memory leaks, so you need to take around with you a pointer to the Inside instance, and this is pretty unconfortable!

How would you do?

>>16 and >>6
Actually the point is not "what language should I use", but "what strategy is better". Also: frozenvoid, stop with your bullshit, I know you want to be worshipped, but here we are talking about C++, not about you.

>>4's solution is good, but asking it to the programmer would divert him from the BUSINESS LOGIC for language related issues. I don't think this would be a good thing.