I ran into this during plugin development and tracked down the cause a while ago with headless tests (Unity 2018.1.9f2, running VaM's own Assembly-CSharp.dll and mcs.dll), and how it could be fixed.
I'll share my findings here since the fix seems quite small, and I've now confirmed it inside...