5. The section on constructor forwarding seems to imply that constructors are the only thing that will be forwarded, when of course that's not the case.
Shoudn't the forwarding stuff be integrated into the forward adaptor instead? Since, it does emulate fowarding for C++03 compilers. The only thing is, it doesn't use rvalue references when they are available.(which should be fairly trivial to support).
6. These sentences don't make sense to me together. They have no obvious connection to one another. To which limitations are you referring?
Fortunately, most constructors take arguments by value, by const-reference or by rvalue reference. If these limitations are accepted, the forwarding emulation of a N-argument case requires just N overloads. This library makes this emulation easy with the help of BOOST_FWD_REF and boost::forward
As far as I can tell from the implementation, BOOST_FWD_REF just generates a const& in emulation mode, which isn't much of an emulation at all.
Ultimately, it should be a non-const reference when using the forward adaptor in emulation mode.