ID 222026 - Metadata values for 'exr/dataWindow' and 'exr/displayWindow' are 1 pixel smaller than expected when rendering EXRs

Problem summary:

When rendering an EXR the bounding box metadata values are 1 pixel smaller for the top right bbox values.

Footage rendered at a bbox of (0, 0, 1920, 1080) will have metadata (0, 0, 1919, 1079) 

Customer reported version:
Nuke 9.0v8

Customer reported platform:
Windows 7

Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph.

2) Select any format in the CheckerBoard's Properties, such as 1920x1080.

3) Create a Write node, and render an EXR file.

4) Create a Read node, and load the rendered EXR file.

5) In the Read node's Properties, switch to the Metadata tab and search for "Window", observing how exr/dataWindow and exr/displayWindow both equal (0, 0, 1919, 1079):

Expected behavior:
When creating EXR files, the exr/dataWindow and exr/displayWindow metadata values should match the original bounding box.

Actual behavior:
The exr/dataWindow and exr/displayWindow metadata keys for EXR files created by Nuke are one pixel lower than the format:

1920x1080 = (0, 0, 1919, 1079)

2048x1556 = (0, 0, 2047, 1555)

Workaround:
No known workaround at this time

Reproduced by Support in:

Nuke 15.0v4 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10

Earliest version tested:
Nuke 12.0v1 - This issue appears to be in all tested versions of the product