Design issue in wrapping "C" API into OO wrapper

I am trying to build an object oriented wrapper, which will wrap API specification; this includes a many structures, events, and APIs. This API specification will be revised every year, there by releasing new specification; the updates are likely to have newer structures, events and APIs. Updates will also include Updates to existing structures, events and APIs, the APIs as such does not change but as they take various structures as parameters which eventually have updates

The challenges

1. The API specification is nothing but an SDK to a lower layer, what I am trying to build is also an SDK but will be an object orient wrapper over this SDK.
2. The requirement is that the users want Objects and methods and no “C” like structures and APIs
3. The frequent version change should not have any impact on high level application and should seamlessly work with any underlying API version
4. Older application should work on newer APIs
5. Newer application should work on older APIs

The last one is a tricky one, what I mean is that the newer application when it sees that it an older version of SDK should somehow transform itself to an older version of API

Is there any design pattern which will help me achieve this task and tied over the frequent changes to internal data and also achieve backward compatibility and forward compatibility?

OS: Windows Dev Environment : Visual C++