Typically, when trying to decouple classes I use Inversion of Control. Lately I've been using a third-party library whose components are sealed. Are there any design patterns to handle this situation? They have multiple component classes that're sealed and I quite often need to use them. I was about to inherit from it and give it an interface to operate through until I noticed it was sealed and impossible to do so.
The library doesn't change a whole lot (only in major versions) so I could pretty easily get away with keeping the classes coupled in this particular scenario, however this has got me wondering about cases where this would not be the case.
How do you keep coupling low in your code when using third-party sealed classes?