Luckily a fix was already available. I updated to the latest Automapper version (12.0.1 at the moment of writing) and the issue disappeared.