I have an object
Window::Window(Renderer & render)
: m_renderBuffer(render) // sometimes looks like this
m_multipleBuffer.push_back(RenderBuffer(render)) // othertimes can look like this
You could simply provide your own version of a move constructor. For example, you can provide a constructor which takes an additional "move" flag, and when the copy constructor is called for an object which has this flag set, it just performs a move instead of a copy.
This technique was described by Bjarne Stroustrup in his keynote at Going Native 2012, when asked how C++ developers implemented moves before C++11.
Also, while I haven't worked with this particular library, there is Boost.Move which emulates move semantics for C++03 compilers. Movable classes get special move constructors and move assignment operators which are distinguished by having a
BOOST_RV_REF(T) argument and which are called using
T a(boost::move(b)) or
T a = boost::move(b).