nope it doesn’t and it’s a tricky one, because support for mocking inline classes requires the @JvmInline annotation which was introduced in kotlin 1.5.
so, besides it not being a trivial implementation, it requires porting mockk to kotlin 1.5 and making sure it remains backwards compatible with projects developed with kotlin 1.4.* and 1.3.*
(porting to 1.4 was a bit of a pain already)