Pseudo views show differently calculated (and incorrect) addresses for variable compared with HLIL

Bug Description:
Pseudo-C and Pseudo-Rust show different addresses next to a variable in the example binary above that do not align with HLIL or Disassembly.

Steps To Reproduce:
Just go to the function sub_401332 in the attached binary as an example.

Expected Behavior:
The variable var_c should be associated with the address 0x00401343.

Screenshots/Video Recording:

In this screenshot, you can see that HLIL correctly shows int32_t var_c = 0 associated with address 0x00401343 while Pseudo-C (on top) incorrectly shows the C equivalent as being associated with address 0x00401332:

And, in this screenshot, we can see that Pseudo-Rust shows the same (incorrect) address as Pseudo-C. We can also verify in Disassembly, on the bottom, that the mov [rbp-0x4], 0x0 is at address 0x00401343, which matches HLIL:

Binary:
example_strippted_intel.zip

Additional Information:
Reported by a user in Slack.

Start with the attached example_strippted_intel.zip and inspect function sub_401332 in the Pseudo-C and Pseudo-Rust views alongside HLIL and Disassembly. Trace why var_c is associated with 0x00401332 instead of the expected 0x00401343; done means both pseudo views align with HLIL and the mov instruction address.