If that's the latest release, that may be the search function not acknowledging the transparent DOS-437 to Win-1252 translation. Or said translation step otherwise messing with search. I dunno.
So lets say you did that, with a clean copy, it'd default to "source is 437, translate it to 1252 so the accent marks are correct". You add those e-acutes, which are byte value 0xE9 (also U+00E9 what a coincidence) in Win-1252. You save the resource, and it gets translated back to DOS-437, so the e-acute is now byte value 0x82.
If the search feature doesn't include that translation step, you're looking for the e-acute with an 0xE9, because that's how Windows does it, but none of the resources actually contain that byte -- it's 0x82, because that's the point in the font resources that looks like an e-acute.