That's not so easy as DCG doesn't remember where the active front is from one mission to the next. So it requires some new code.
I agree with you.
But only you can do it, if it is your will.
However, DCG is already able to link this static objects to a garrison.
"Determining the nearest location on the map to a static object." (from the dcgerror.txt file) seems to be an usual call to an existing function/procedure.
And they are always located nearby a waypoint. The first/last for one side, the third/antepenultimate for the other side.
In an other way, the static object ID can locate it.
Extract from the territory.dcg file:
Nitra_Supply_Depot 2 allied=0 axis=99
Nitra_Bridge68 2 allied=0 axis=20
Nitra_Power_Plant 2 allied=0 axis=40
Cerman 2 allied=0 axis=30
Horne_Krskany 2 allied=0 axis=70
Nitra_Airfield 2 allied=0 axis=0
Nitra_Airstrip 2 allied=0 axis=130
Hrnciarovce 2 allied=0 axis=20
Mlynarce_Ferry 2 allied=0 axis=30
Capor 2 allied=0 axis=30
Dolne_Krskany 2 allied=0 axis=70
Velke_Janikovce 2 allied=0 axis=30
Pograny 2 allied=0 axis=20
Stitare 2 allied=0 axis=20
DrazovceC3_Ferry 2 allied=0 axis=30
Sarluzky 2 allied=0 axis=20
Lehota 2 allied=0 axis=20
Mocenok 2 allied=0 axis=20
Svatoplukovo 2 allied=0 axis=30
Ivanka_Pri_Nitre 2 allied=0 axis=70
Saying that Cerman is the contested location.
It is line #4 in the territory.dcg file. So stactic objects can be 400101, 400102, 400103... for the allied side and 400201, 400202, 400203... for the axe side.
So, parsing the log, if DCG read that the "1000102_Static is destroyed by NAST-idefix44:Bf-109G-6 at 38798.74 45271.54", it decreases the Capor allied garrison value (-9)...