Fixed wrong 'following bytes' information in TCP proxy

AMWD.Protocols.Modbus.Common/Contracts/ModbusClientBase.cs

@@ -1,9 +1,9 @@
 using System;
 using System.Collections.Generic;
-using System.Threading.Tasks;
-using System.Threading;
 using System.Linq;
 using System.Text;
+using System.Threading;
+using System.Threading.Tasks;
 
 namespace AMWD.Protocols.Modbus.Common.Contracts
 {

AMWD.Protocols.Modbus.Common/Exceptions/ModbusException.cs

@@ -1,6 +1,8 @@
 using System;
 using System.Diagnostics.CodeAnalysis;
+#if !NET8_0_OR_GREATER
 using System.Runtime.Serialization;
+#endif
 
 namespace AMWD.Protocols.Modbus.Common
 {

AMWD.Protocols.Modbus.Common/Models/ModbusObject.cs

@@ -1,4 +1,6 @@
-using System;
+#if NET6_0_OR_GREATER
+using System;
+#endif
 
 namespace AMWD.Protocols.Modbus.Common
 {

AMWD.Protocols.Modbus.Common/Protocols/RtuOverTcpProtocol.cs

@@ -10,7 +10,9 @@ namespace AMWD.Protocols.Modbus.Common.Protocols
 	/// </summary>
 	/// <remarks>
 	/// The Modbus RTU over Modbus TCP is rarely used.
-	/// It is a non-standard variant of Modbus TCP that includes wrapps a Modbus RTU message within a Modbus TCP message.
+	/// It is a non-standard variant:
+	/// You can define it as RTU message with an additional TCP header
+	/// or as TCP message with an additional CRC16 checksum at the end (header not included!).
 	/// <br/>
 	/// Definition found on <see href="https://www.fernhillsoftware.com/help/drivers/modbus/modbus-protocol.html">Fernhill Software</see>.
 	/// </remarks>