Bump replaced with answer..
After MUCH hair being pulled out (which is a problem, see my avatar picture) I finally found the issue..
Thank you Pro T-SQL 2012 Programmer's Guide by Jay Natarajan (et all)
Page 267
HEMISPHERE AND ORIENTATION
You need also to specifiy the right ring orientation. So why is ring orientation so important, and what is the
“right” ring orientation? To answer these questions, you have to ask yet another question: “What is the inside
of a Polygon?” You might instinctively say that the inside of a Polygon is the smallest area enclosed by the
coordinates you supply. But you could end up in a situation where your Polygon should be the larger area
enclosed by your coordinates. If you created a border around the North Pole, for instance, is your Polygon
the area within the border or is it the rest of the Earth minus the North Pole? Your answer to this question
determines what the “inside” of the Polygon really is.
The next step is to tell SQL Server where the inside of the Polygon lies. SQL Server’s geography instance
makes you define your coordinates in counterclockwise order, so the inside of the Polygon is everything that
falls on the left-hand side of the lines connecting the coordinates.
...........
This eliminates any ambiguity from your Polygon definitions.
(All rights remain with the author and I am only claiming fair use)
It seems that my polygon is defined in the clockwise manner which apparently means that my polygon is defining the OUTSIDE of the polygon, this means that the results I was getting make COMPLETE sense now.. It also means that some of my data is defined clock-wise and other is defined counter clock-wise.. Sooooooo I'll have to fix that..
CEWII