Always-on-top in taskmgr is not as strong as it should be

Reproduction steps

• run "Chromium XP 49 VS2015" from rapps
• run our taskmgr in parallel
• make sure that the taskmgrs "Always On Top" checkbox is checked (that is the default)
• move the taskmgr in front of Chromium
• now make Chromium the active Window

Expected result
The taskmgr should be topmost, and should not be covered by the Chromium window
This is what our taskmgr already manages to achieve if we do run it on Windows XPSP3, tested the same against that same Chromium version

Observed result
if we do perform the same within ros, suddenly Chrome is stronger (more topmost) than the taskmgr
0.4.15-dev-7842-g558ab78_taskmgrsAlwaysOnTopIsNotPowerfulEnough.webm
0.4.15-dev-7842-g558ab78_taskmgrsAlwaysOnTopIsNotPowerfulEnough.log

I do deduce from that test-outcome that it is not the taskmgr binary that has the bug, but maybe some issue in Win32SS prevents the proper topmost order here.

Edit: I hereby want to simplify the reproduction steps! You can just use notepad and our taskmgr to reproduce the bug, no need for 3rd-party Chromium-XP at all.