Hello, I'am coding for a long time on STM32F1 boards. But Intellisense is broken from start for both Dan Drown's and STMicroelectronic (stm32duino) cores. Looks like there's something bad with headers.

Typical IntelliSense errors are:
sscanf/sprintf/.../e.t.c stdio functions (Too many arguments)
minmax/abs/.../e.t.c cmath functions
inttypes like uint8_t, int32_t wasn't working in previous VisualMicro versions (sense telling that they're not defined), but now they are seems to be working somehow.

Versions:
Visual Studio 2019
Visual Micro 2021.427.0
stm32duino core 2.0.0
Dan Drown's core 2021.3.18

Note that's only IntelliSense problem, building and uploading working as they should, but IntelliSense errors are quite annoying.

There's a simple project to reproduce. (you can use STM32F103C8T6 board is used as example)

Ok, so I'am opened project (which was zipped in this thread) on other PC (cause I don't have access to original PC I'am working on) and sscanf/sprintf shows correct IntelliSense. But, when I'am opening my old project IntelliSense is even more broken, sscanf/sprintf/e.t.c are undefined, though build working just fine. There's output log for old project where IntelliSense doesn't work. 
I suppose there is a dependency from windows sdk version or something...

UPD: In my old project .ino file name and .vcxproj names are different, may be this is the problem, now when I've renamed .vsxproj file and readded all sources (that is why I haven't renamed it before, cause whole project files are broken) IntelliSense is working correct, at least on this machine. Once I've get access to my other PC I'll check it there (may take smth around month)

UDP2: After build memset/strncpy/sscanf/e.t.c (at least) prompted as undefined :c .Although cstring and memory are included. And was working right five minutes ago.

UDP3: Looks like once when I choose "Release" build in top panel (which I actually want to) IntelliSense going crazy. But when I switch back to Debug it's ok. May be I've got it incorrect and this Solution Configuration is not for real Visual Micro Debug/Release, but whole time I thought so.