Fix function naming conflict with class overloads.

This fix takes into account the classname while generating overload
handlers.

Example:

If you have two classes:

  class A {
    public:
      void doSomething(int);
      void doSomething(double);
  };

  class B {
    public:
      void doSomething(int);
      void doSomething(double);
  };

Before this patch, the overload handlers for A::doSomething and
B::doSomething create conflicting names and function redefinition errors
are caused.

After the patch, the overload handlers are named classname_doSomething
and no longer conflict.

This is might not the best way to implement this, but it
solves a critical problem on large projects, and specifically can affect
operator overloads that are being wrapped.
Bump version to 3.0.3
Merge trunk at commit '8728a97dc60417e4c5599349d06cd1c408f14a7d' into travis-osx

* commit '8728a97dc60417e4c5599349d06cd1c408f14a7d':
  Bump version to 3.0.3
  Fix function naming conflict with class overloads.