Intel compiler on Windows bug workarounds

There is a tension between the Visual Studio point release and Intel compilers on Windows. The issue arises from Visual Studio frequently updating, and Intel compiler falling behind with the Intel compiler to Visual Studio ABI. This can cause strange and unpredictable errors when compiling a C program, for example

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.23.28105\include\vcruntime_string.h(18): error: expected an attribute name
  _NODISCARD _Check_return_


Intel support notes that a workaround is to force C++ compiler to be used with the /Tp<source_filename> option.

This replaces the usual /c<source_filename> option. Since this is a Windows issue, this command is likely inside each response .rsp file used to compile each source code file.