For example:

class Managed
{
    Managed(const Managed &other);
    void operator = (const Managed &other);

public:
    Managed();
    Managed(int foo);
    virtual ~Managed();

    void *operator new(size_t size, MemoryPool *pool);
    void operator delete(void *);
    void operator delete(void *, MemoryPool *);
};

This class *must* be created like this:

MemoryPool mem;
Managed* m = new (&mem) Managed;
Managed* m2 = new (&mem) Managed(2);

IMO, shiboken would create a new Python constructor for each existent
constructor and prepend all extra arguments needed by the new overload, so the
Python user would do:

mem = MemoryPool()
m = Managed(mem)
m2 = Managed(mem, 2)

The ideal situation would be to completely hide the MemoryPool class, but
sometimes it's not possible.