The "Optmized" applies to the Nested Loops operator, and it means that this particular operator was not using a specific "optimized" shortcut. To be perfectly honest, what exactly this mean, I don't know on the top of my head.
The percentage you see applies to the estimates, not the actual cost. So the optimizer thinks the plan with Nested Loops is better, but it may be wrong.
To find out which query that is better you would do something like:
DECLARE @d datetime2(3) = sysdatetime()
-- Run query
SELECT datediff(ms, @d, sysdatetime())
Although, since this is a SELECT query, the time can be distorted by the time it takes for SSMS to render the data. And with this small data set, the times will be so small, that it is difficult to draw conclusions anyway.