Fast up to date always fails when using bebop-tools with VS2022

[Romanx]

Describe the bug
Because the compiler always runs the code file is always updated on the disk and so the fast up to date check always fails since the file is newer than the time the build started.

VS2022 seems to have made this give more output information and so this only appears in VS2019 although the problem will probably exist.

To Reproduce
Steps to reproduce the behavior:

1. Create a dotnet project using VS2022.
2. Add bebop and bebop-tools.
3. Add a bop file and csproj elements to compile it at build.
4. Look in the output window on build, it should say WARNING: Potential incremental build failure in '_project_'. See: https://aka.ms/incremental-build-failure
5. To see the below snippet turn on up to date check logic as explained in the link in step 4.

Expected behavior
The generated file should not be updated if the schema file hasn't been changed.

Screenshots / Snippets

3>FastUpToDate: Input Compile item 'C:\Projects\TestProject\ResultFile.g.cs' (26/05/2022 11:42:25) has been modified since the last successful build started (26/05/2022 11:42:24), not up-to-date. (TestProject)
3>FastUpToDate: Up-to-date check completed in 1.1 ms (TestProject)

Bebop info:

• Version: 2.4.2
• Runtime: .NET

Desktop (please complete the following information):

• OS: Windows
• Version 10

Additional context
Details about the fast up to date check can be found here.