Templated renderer class
Another approach, the first one to come to my mind actually, would be using a std::type_index as key in your unordered_map. That's exactly what type_index was designed for, and it is more specific about its purpose than a raw size_t integer.
BTW, size_t is a member of namespace std in C++, so if you are going to use it, make sure to properly qualify the type as std::size_t. The C++ standard does not require it to also be available in the global namespace. You should also include &lt;cstddef&gt; somewhere (the header that defines std::size_t). At the moment you rely on some other standard header that imports this dependency.
I really don't like this:


void (*f)(Shader*, T&amp; )

reinterpret_cast&lt; void(*)(Shader* shd, T&amp; t) &gt;(rp)( shd, obj );



First issue here is the duplicate typing of this function's signature. If you introduce a typo in any of the declarations, that could very well crash de program, because it would be using a different signature from the actual function. This can be improved with a local typedef. Second is the type cast from RenderFunctionPointer to the actual pointer type. It looks dangerous. Third, std::function would be a much better and type-safe option.

According to feedback from a comment, this approach was taken to account for different functions for different types of objects. The template type T can be anything, however the map has to store a known type.

Since you are already paying for the price of an indirect function call, then perhaps a cleaner approach would be to use polymorphism. Make the object type inherit from a Renderable interface that has a onRender(Shader &amp; shd) virtual method. That would also remove the need to store function pointers into the renderer, cleaning up the interface as well. Instead of telling the renderer how to draw an object, let the object know how to draw itself.
You don't need these typedefs:


typedef std::unordered_map&lt; size_t, Shader* &gt;::iterator ShaderIterator;
typedef std::unordered_map&lt; size_t, RenderFunctionPointer &gt;::iterator FunctionIterator;



If your sole objective is to reduce typing in places like this:


ShaderIterator i = Shaders.find( type );



That is what auto is for (C++11).
I see that you have a macro wrapping your log system (LOG_WARNING()). However, even if you mute your log by changing an internal verbosity parameter, the log calls would still be evaluated. I'm assuming this will be used for software like video games, where you probably don't need the overhead of logging on a released title. So I would suggest that you change you logging macros a little bit to avoid evaluating the log calls if you ever wish to mute the log system permanently (such as in a release build):

#define LOG_WARNING(msg) do { MyLog::getInstance() &lt;&lt; msg &lt;&lt; "\n"; } while (0)


That's one possibility. Then if you need to disable it, just make the macro a no-op:

#define LOG_WARNING(msg)


Now when using the log, a small change:

LOG_WARNING("Couldn't find shader for object: " &lt;&lt; typeid( T ).name());


For the muted/disabled log, the logging calls would not be evaluated at all, incurring no runtime cost.
A final comment: The ownership of the Shader instances added to the renderer via AddObjectType() if quite unclear. Who is supposed to free those pointers? The renderer? The caller? No one? In such situations, the best solution is almost always to use a smart pointer. Perhaps a std::shared_ptr would be adequate in this case, if ownership is meant to be shared. Otherwise, a std::unique_ptr would be the best course of action.