There can be workarounds for lack of matrix inverse support, such as introducing auxiliary variables and constraints. However, as I have all too painfully discovered, in some cases, such workarounds can significantly degrade the model, and you may be best avoiding them. So, for example, calling fmincon or knitro directly from MATLAB may allow you to directly handle matrix inverses, and in some cases be far superior to using YALMIP as a front end and working around lack of matrix inverse support. On the other hand, when the solver itself doesn't support matrix inverses, such as BARON for global optimization, then you're out of luck.
Hint, hint, I'm sure there would be some effort in developing support in YALMIP for matrix inverse, but on the other hand, there is a well-developed matrix calculus for differentiation, including matrix inverse, chain rule, etc. Thanks.